Subject: DLSw summary minutes - AIW8 meeting - Aug 95

From: [email-masked]
Date: Tue, 5 Sep 95 12:06:09 PDT

Data link switchers:
 These are the summary minutes.  The detailed minutes for each
group have been/will be posted by the volunteers who graciously
took the minutes and wrote them up for your benefit.

Regards,
   Louise Wells

---
Data Link Switching (DLSw)
Summary of the work of the DLSw Related Interest Group (RIG)
at the APPN Implementer's Workshop (AIW) #8
August 1995, Raleigh, NC

1.	Connect 
	-	Using non-TCP/IP transports between switches
		.	Will develop 'template' for details each 
			proposed transport must consider
		.	May have separate RFC for each transport type
		.	DLSw RIG or AIW may need an organizationally-
			unique identifier (OUI)

	-	HALT reason codes
		.	Added code to explain why circuit was dropped

	-	Errata / clarifications
		.	Will be listed and posted on ftp server
			with DLSw V1.0 document
		.	Will be fixed in DLSw V2.0 document

2.	Interoperability
	-	The event originally titled "DLSw Connect-a-thon"
		was renamed to the "DLSw V1 Interoperability Test"
	
	-	Is hosted by Bay Networks in Billerica, MA
		on October 2-6

	-	Scheduled times set for DLSw V1 base and option test suite
		(Test suite posted on aiw-dlsw-interoperability mail list)

	-	Time will be set aside for other testing participants may want

	-	This is an engineering test, not a marketing event.
		No participant may report publicly on results of tests.

3.	Management Information Base (MIB)
	-	DLSw MIB document is separate from DLSw document,
		like all other MIBs
	
	-	MIB is complete except for one outstanding issue
		.	Likely to be resolved on network mail list

	-	MIB is in IETF process, not AIW process, like all other MIBs

4.	Scalability
	-	At AIW7 in May, Cisco contributed its Border Peer 
		enhancements as a scalability proposal to group. 

	-	DLSw group decided here to actively pursue increased 
		scalabilityas an option set to DLSw for V2.0

	-	Three separate but coordinated ideas were discussed
		here
		.	Add option to negotiate down to one TCP connection
			per peer
		.	Refine use of IP multicast
		.	Refine Cisco's Border Peer proposal

	-	A proposal which includes all three ideas is due
		by late October